Refactor tests for shared distributions#54863
Conversation
potiuk
requested review from
amoghrajesh,
ashb,
gopidesupavan and
jedcunningham
as code owners
boring-cyborg
bot
added
area:dev-tools
backport-to-v3-1-test
potiuk
removed
the
backport-to-v3-1-test
potiuk
force-pushed
the
dynamic-tests-for-shared-distributions
branch
3 times, most recently
from
8af117b to
1206ea8
Compare
amoghrajesh
left a comment
amoghrajesh
left a comment
There was a problem hiding this comment.
One qn: if changes are made in shared/timezones, will it run tests only for that or for all shared?
All tests. They are fast in case of those shared utils. I prefer to run them always for everything (similarly as we run always all prek hook for |
* Dynamically detect shared distributions in selective checks * Run the tests as matrix * Skip cleaning the worker and setting up docker and breeze * Install the version of uv that we are bound with * Run tests in parallel with xdist
potiuk
force-pushed
the
dynamic-tests-for-shared-distributions
branch
from
1206ea8 to
4f0f343
Compare
|
make sense as these components are very critical running always good choice :). |
Yep, I was expecting that too. The shared components also could inter depend on each other, so it would make sense too |
|
Random k8s tests |
|
Nice thanks @potiuk! |
* Dynamically detect shared distributions in selective checks * Run the tests as matrix * Skip cleaning the worker and setting up docker and breeze * Install the version of uv that we are bound with * Run tests in parallel with xdist
* Dynamically detect shared distributions in selective checks * Run the tests as matrix * Skip cleaning the worker and setting up docker and breeze * Install the version of uv that we are bound with * Run tests in parallel with xdist
4 participants
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.